Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a660fdec22813732034061169cb6fb8f84df49efdd6b049a5d6e8dbea11fb159

Tx prefix hash: e127e62f4bf23a9ceaa90516418ccb8e5bf6cbb5905f50d5b4dfc47ef26cd2f4
Tx public key: 072b3d34f8921a957e76c73123ec5d268e860ddbfde74dd54628a934988b7064
Timestamp: 1701277389 Timestamp [UCT]: 2023-11-29 17:03:09 Age [y:d:h:m:s]: 01:123:05:10:56
Block: 902331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349222 RingCT/type: yes/0
Extra: 01072b3d34f8921a957e76c73123ec5d268e860ddbfde74dd54628a934988b706402110000000133af99f4000000000000000000

1 output(s) for total of 0.628391710000 dcy

stealth address amount amount idx
00: 1babbf027a38f97d3cf835b06faa187c9592dcff4f8ae002e20cec06d952c4c0 0.628391710000 1358964 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": 902341, "vin": [ { "gen": { "height": 902331 } } ], "vout": [ { "amount": 628391710, "target": { "key": "1babbf027a38f97d3cf835b06faa187c9592dcff4f8ae002e20cec06d952c4c0" } } ], "extra": [ 1, 7, 43, 61, 52, 248, 146, 26, 149, 126, 118, 199, 49, 35, 236, 93, 38, 142, 134, 13, 219, 253, 231, 77, 213, 70, 40, 169, 52, 152, 139, 112, 100, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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