Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15846e3e82dc8996bac0366cf2286792eef80a4d9152597c187b6cdca01d041d

Tx prefix hash: 47b60240e6d395c1e13862119512fd0c3e6033d4e35ddb0947c177b1b6bf854d
Tx public key: 436ed56222e0ba5adaaa945db07f47be1df81a28a69c3f111e17eb5ff8c7cdea
Timestamp: 1715018502 Timestamp [UCT]: 2024-05-06 18:01:42 Age [y:d:h:m:s]: 01:022:09:41:21
Block: 1016262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276956 RingCT/type: yes/0
Extra: 01436ed56222e0ba5adaaa945db07f47be1df81a28a69c3f111e17eb5ff8c7cdea0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e02cad24c38fb50a717856f32fad963d2aa0ba728bb7a3631964c2d3d1b47fbd 0.600000000000 1479793 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": 1016272, "vin": [ { "gen": { "height": 1016262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e02cad24c38fb50a717856f32fad963d2aa0ba728bb7a3631964c2d3d1b47fbd" } } ], "extra": [ 1, 67, 110, 213, 98, 34, 224, 186, 90, 218, 170, 148, 93, 176, 127, 71, 190, 29, 248, 26, 40, 166, 156, 63, 17, 30, 23, 235, 95, 248, 199, 205, 234, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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