Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd0f870cc461924a4027b43d4f39ec599d224d888591a91be61abf46cea6b4d3

Tx prefix hash: e38133a2701919ff534a2c3a5227269197754ebcaa4b79dee69b355b0f6dedd9
Tx public key: 4244c322586fe8a117aa56d080a1f4de645ffb45ceccb4efbb7ac31ce1f93997
Timestamp: 1714218872 Timestamp [UCT]: 2024-04-27 11:54:32 Age [y:d:h:m:s]: 01:196:14:18:51
Block: 1009625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399148 RingCT/type: yes/0
Extra: 014244c322586fe8a117aa56d080a1f4de645ffb45ceccb4efbb7ac31ce1f939970211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9249547df8d19f2d2826194e73f0d9efa962f6d2a5f89e7ac6aadf6bb9c411f6 0.600000000000 1471353 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": 1009635, "vin": [ { "gen": { "height": 1009625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9249547df8d19f2d2826194e73f0d9efa962f6d2a5f89e7ac6aadf6bb9c411f6" } } ], "extra": [ 1, 66, 68, 195, 34, 88, 111, 232, 161, 23, 170, 86, 208, 128, 161, 244, 222, 100, 95, 251, 69, 206, 204, 180, 239, 187, 122, 195, 28, 225, 249, 57, 151, 2, 17, 0, 0, 0, 1, 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