Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 119f40145c988786d523ebae6917aa3c3f20d716ed293b21b6d1fd867da22ce9

Tx prefix hash: 2630e95f65e2f5ab924fbd0fe3d157afcaffc62bd4de0706e9b18f7abbd3d682
Tx public key: 9e524ffe0903f2836f221cb323cc56e1d876c82915b263c9480663e79232d899
Timestamp: 1715549732 Timestamp [UCT]: 2024-05-12 21:35:32 Age [y:d:h:m:s]: 00:307:14:41:06
Block: 1020690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219860 RingCT/type: yes/0
Extra: 019e524ffe0903f2836f221cb323cc56e1d876c82915b263c9480663e79232d899021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a123eeaa53d06c0358954ff722a17d3474fd2f714073663d20401af687f252ae 0.600000000000 1484771 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": 1020700, "vin": [ { "gen": { "height": 1020690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a123eeaa53d06c0358954ff722a17d3474fd2f714073663d20401af687f252ae" } } ], "extra": [ 1, 158, 82, 79, 254, 9, 3, 242, 131, 111, 34, 28, 179, 35, 204, 86, 225, 216, 118, 200, 41, 21, 178, 99, 201, 72, 6, 99, 231, 146, 50, 216, 153, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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