Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53342d4ff8819f2333e2731f3d16242a828cef6712d02eb90f9ebdd595366bce

Tx prefix hash: 62cae4e3a8396d346b9a13ad45c18fb0726e417d8f8fdf386b273d7e15b79b73
Tx public key: e6f9bb6a441430110982b1a550d1ac60f905e76b6fa05220ccef651aa73391b5
Timestamp: 1686386499 Timestamp [UCT]: 2023-06-10 08:41:39 Age [y:d:h:m:s]: 02:151:21:43:01
Block: 779139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 628322 RingCT/type: yes/0
Extra: 01e6f9bb6a441430110982b1a550d1ac60f905e76b6fa05220ccef651aa73391b502110000000533af99f4000000000000000000

1 output(s) for total of 1.608382049000 dcy

stealth address amount amount idx
00: e1c02e8d4c3cfc2cf15a8d71a70a7bbdcd61428489cfbded765c9a34002870a7 1.608382049000 1228784 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": 779149, "vin": [ { "gen": { "height": 779139 } } ], "vout": [ { "amount": 1608382049, "target": { "key": "e1c02e8d4c3cfc2cf15a8d71a70a7bbdcd61428489cfbded765c9a34002870a7" } } ], "extra": [ 1, 230, 249, 187, 106, 68, 20, 48, 17, 9, 130, 177, 165, 80, 209, 172, 96, 249, 5, 231, 107, 111, 160, 82, 32, 204, 239, 101, 26, 167, 51, 145, 181, 2, 17, 0, 0, 0, 5, 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