Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c15815a09796cb3174f995dd612c60bf5349246105becf0957d3cf7fd333cfb3

Tx prefix hash: b0a1a64a5f6f4a5c81fe701b30b23e8d70b780734e3eb9e6c1551fa4e043d933
Tx public key: 28d450dc7742e86c970290354344c3a1859e54e11b6a6089f718fdeb7e1ebeff
Timestamp: 1687575464 Timestamp [UCT]: 2023-06-24 02:57:44 Age [y:d:h:m:s]: 01:246:01:34:27
Block: 789005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436970 RingCT/type: yes/0
Extra: 0128d450dc7742e86c970290354344c3a1859e54e11b6a6089f718fdeb7e1ebeff02110000000375e3f0e9000000000000000000

1 output(s) for total of 1.491760315000 dcy

stealth address amount amount idx
00: 5325fd5b0c747fe99ad9657263abffee1e5af3bbd9e7c95ae8bf6497d514e858 1.491760315000 1239174 of 0

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": 789015, "vin": [ { "gen": { "height": 789005 } } ], "vout": [ { "amount": 1491760315, "target": { "key": "5325fd5b0c747fe99ad9657263abffee1e5af3bbd9e7c95ae8bf6497d514e858" } } ], "extra": [ 1, 40, 212, 80, 220, 119, 66, 232, 108, 151, 2, 144, 53, 67, 68, 195, 161, 133, 158, 84, 225, 27, 106, 96, 137, 247, 24, 253, 235, 126, 30, 190, 255, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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