Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 601a9424f9ce3b80ef7949e1fd09c466b2752d86a40c61ac6c1603663e2543c1

Tx prefix hash: 6c6f5c9b97038fcb2d827f3eff7aaeb1152239dafbd9bfdb1b059702ed3eb734
Tx public key: ac7f7a69f08290440cc0f740aeeaeda767b8e3edff96d6e164b4742b2d139f45
Timestamp: 1722506468 Timestamp [UCT]: 2024-08-01 10:01:08 Age [y:d:h:m:s]: 00:310:16:51:19
Block: 1078327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222010 RingCT/type: yes/0
Extra: 01ac7f7a69f08290440cc0f740aeeaeda767b8e3edff96d6e164b4742b2d139f4502110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 941bcdc01c8d54ea7788a94fd4df8120ea488e0e5f06a1539450b026f242a3d8 0.600000000000 1550904 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1078337, "vin": [ { "gen": { "height": 1078327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "941bcdc01c8d54ea7788a94fd4df8120ea488e0e5f06a1539450b026f242a3d8" } } ], "extra": [ 1, 172, 127, 122, 105, 240, 130, 144, 68, 12, 192, 247, 64, 174, 234, 237, 167, 103, 184, 227, 237, 255, 150, 214, 225, 100, 180, 116, 43, 45, 19, 159, 69, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8