Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4404c05977efd7f6d23eee24a8be684e3350f4ecee1c3a90e72f0dd7b91c861

Tx prefix hash: ea83ecde7c0a64e3fb572770effde2a05d01ed2354e6abebb807551568e5f06b
Tx public key: 23e9fe4a881ccf3d70e1a4e8ad5f022f6cacd0370d715d6a9f387cbd1d1bb36e
Timestamp: 1577701922 Timestamp [UCT]: 2019-12-30 10:32:02 Age [y:d:h:m:s]: 05:108:22:46:32
Block: 34947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1227663 RingCT/type: yes/0
Extra: 0123e9fe4a881ccf3d70e1a4e8ad5f022f6cacd0370d715d6a9f387cbd1d1bb36e02110000000d8a2ee0d9000000000000000000

1 output(s) for total of 470.118061659000 dcy

stealth address amount amount idx
00: 8f3f252975ed46019a6e3f7de6256c9f8bbe5bb95a76995cd51917b742397b50 470.118061659000 58864 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": 34957, "vin": [ { "gen": { "height": 34947 } } ], "vout": [ { "amount": 470118061659, "target": { "key": "8f3f252975ed46019a6e3f7de6256c9f8bbe5bb95a76995cd51917b742397b50" } } ], "extra": [ 1, 35, 233, 254, 74, 136, 28, 207, 61, 112, 225, 164, 232, 173, 95, 2, 47, 108, 172, 208, 55, 13, 113, 93, 106, 159, 56, 124, 189, 29, 27, 179, 110, 2, 17, 0, 0, 0, 13, 138, 46, 224, 217, 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