Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 561ea01967e30a2fc78e5fddb1d4ff9015925113d785624db228d86ad2a56ea7

Tx prefix hash: 641eb09d1f9713131ae98da3032ecacfbbbe1b2f4c5ff92cb585d164d4460a84
Tx public key: bd2feb37f08f9466d0e3703880f9a383f15895afc7eeafb1ed7fad46a1e6452c
Timestamp: 1656009131 Timestamp [UCT]: 2022-06-23 18:32:11 Age [y:d:h:m:s]: 02:197:07:45:29
Block: 528826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 662325 RingCT/type: yes/0
Extra: 01bd2feb37f08f9466d0e3703880f9a383f15895afc7eeafb1ed7fad46a1e6452c021100000009e6d27f9c000000000000000000

1 output(s) for total of 10.858756617000 dcy

stealth address amount amount idx
00: 033d70a9679989678c0acd5b96457d3f32eddbeaa166e31abed06c722152a106 10.858756617000 957689 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": 528836, "vin": [ { "gen": { "height": 528826 } } ], "vout": [ { "amount": 10858756617, "target": { "key": "033d70a9679989678c0acd5b96457d3f32eddbeaa166e31abed06c722152a106" } } ], "extra": [ 1, 189, 47, 235, 55, 240, 143, 148, 102, 208, 227, 112, 56, 128, 249, 163, 131, 241, 88, 149, 175, 199, 238, 175, 177, 237, 127, 173, 70, 161, 230, 69, 44, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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