Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c820e0aad8a95de1f389def8d2b4cc033ea45bc8b3b8458c27fbf4d7e21fdab8

Tx prefix hash: 36d27342406b1534d02ac4a01974c70956a5b2aecda2f225180f3175a47f3910
Tx public key: 4739b2905b7564a9372f2a1033b64eaeb39bebc21551ce8a1d23fd979d2dd61c
Timestamp: 1710514663 Timestamp [UCT]: 2024-03-15 14:57:43 Age [y:d:h:m:s]: 01:037:23:53:43
Block: 978937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288127 RingCT/type: yes/0
Extra: 014739b2905b7564a9372f2a1033b64eaeb39bebc21551ce8a1d23fd979d2dd61c02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4a673a003129f1ab39320afe9df2ffc9452fb87eaf793c735bee879fa3097e6 0.600000000000 1438966 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": 978947, "vin": [ { "gen": { "height": 978937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4a673a003129f1ab39320afe9df2ffc9452fb87eaf793c735bee879fa3097e6" } } ], "extra": [ 1, 71, 57, 178, 144, 91, 117, 100, 169, 55, 47, 42, 16, 51, 182, 78, 174, 179, 155, 235, 194, 21, 81, 206, 138, 29, 35, 253, 151, 157, 45, 214, 28, 2, 17, 0, 0, 0, 11, 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