Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5996932c72fae6b9aae45150a3bd2ca131bbb756bc6c7ba5d54c65cf3fa8ddc0

Tx prefix hash: 89dd5905d1ae7ae6c9fdf5dab5b7a0b80ad80f8df7e2872ed1393675a428dae6
Tx public key: e79266ba4e0c3c33e422862885063c76974a72751d8cea701eb2fc1dfb35f1ec
Timestamp: 1705013646 Timestamp [UCT]: 2024-01-11 22:54:06 Age [y:d:h:m:s]: 01:068:09:09:17
Block: 933296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309992 RingCT/type: yes/0
Extra: 01e79266ba4e0c3c33e422862885063c76974a72751d8cea701eb2fc1dfb35f1ec0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d7c1acad464ffe40bdeaccf530569ad89d3a72e592a3436374414ccbaaf2083 0.600000000000 1391258 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": 933306, "vin": [ { "gen": { "height": 933296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d7c1acad464ffe40bdeaccf530569ad89d3a72e592a3436374414ccbaaf2083" } } ], "extra": [ 1, 231, 146, 102, 186, 78, 12, 60, 51, 228, 34, 134, 40, 133, 6, 60, 118, 151, 74, 114, 117, 29, 140, 234, 112, 30, 178, 252, 29, 251, 53, 241, 236, 2, 17, 0, 0, 0, 1, 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