Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e345634cbb4752c3720ba85aa6d55ed8ba08630358677e540ce9e67fe516324b

Tx prefix hash: 0d41c788d865c836fc824be0f9d18c037ca3a70420d5fcb086e7c156fbc04b32
Tx public key: 23f28d6b41302e26a8887578ae5e581e312de2e8f9ba94f583f2b158ab62d0ac
Timestamp: 1714964833 Timestamp [UCT]: 2024-05-06 03:07:13 Age [y:d:h:m:s]: 00:332:23:37:34
Block: 1015809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238012 RingCT/type: yes/0
Extra: 0123f28d6b41302e26a8887578ae5e581e312de2e8f9ba94f583f2b158ab62d0ac02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ea3de5acb6678ef20edb11913b7d41576682edbdc284bf993aa4abb7b1165e3 0.600000000000 1479252 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": 1015819, "vin": [ { "gen": { "height": 1015809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ea3de5acb6678ef20edb11913b7d41576682edbdc284bf993aa4abb7b1165e3" } } ], "extra": [ 1, 35, 242, 141, 107, 65, 48, 46, 38, 168, 136, 117, 120, 174, 94, 88, 30, 49, 45, 226, 232, 249, 186, 148, 245, 131, 242, 177, 88, 171, 98, 208, 172, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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