Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6234dba6a03da0867d40de6d28d336411a82e42ebe425c0b94e65163c57a7a17

Tx prefix hash: aeba527791a9db90692ce202a3def4bf2bc474cfd5171944985eaa164242ccf1
Tx public key: bf9d20fdbf6b907a145af1de096e2d824262eb5d2c542f918101eb68205cf46c
Timestamp: 1709314093 Timestamp [UCT]: 2024-03-01 17:28:13 Age [y:d:h:m:s]: 01:012:22:32:15
Block: 968973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270257 RingCT/type: yes/0
Extra: 01bf9d20fdbf6b907a145af1de096e2d824262eb5d2c542f918101eb68205cf46c0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e181e674e1b71cd5d3dd81846a1c2641f8e472304886275c7b45f38f5a9e0fa 0.600000000000 1428800 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": 968983, "vin": [ { "gen": { "height": 968973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e181e674e1b71cd5d3dd81846a1c2641f8e472304886275c7b45f38f5a9e0fa" } } ], "extra": [ 1, 191, 157, 32, 253, 191, 107, 144, 122, 20, 90, 241, 222, 9, 110, 45, 130, 66, 98, 235, 93, 44, 84, 47, 145, 129, 1, 235, 104, 32, 92, 244, 108, 2, 17, 0, 0, 0, 6, 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