Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf1eff61ff0902bd4e7748a4e8506f6b1ff4de0d338c2e8eeff65d00af5606d4

Tx prefix hash: 982483d6940d71c6ecf09adff0c181bc688ed0647c165c416171c4f059403585
Tx public key: d4b08a13a4b2c68d2f347ddcac818951dd4b04e0b80b93cea455b5d94b00724a
Timestamp: 1657022112 Timestamp [UCT]: 2022-07-05 11:55:12 Age [y:d:h:m:s]: 03:119:04:30:29
Block: 537147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 864900 RingCT/type: yes/0
Extra: 01d4b08a13a4b2c68d2f347ddcac818951dd4b04e0b80b93cea455b5d94b00724a0211000000184da16a3a000000000000000000

1 output(s) for total of 10.190820682000 dcy

stealth address amount amount idx
00: 8ae0baafee46fd11d6f96a04520f5d9a81fa58584ba5ad6684a7968955f3e9f0 10.190820682000 967004 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": 537157, "vin": [ { "gen": { "height": 537147 } } ], "vout": [ { "amount": 10190820682, "target": { "key": "8ae0baafee46fd11d6f96a04520f5d9a81fa58584ba5ad6684a7968955f3e9f0" } } ], "extra": [ 1, 212, 176, 138, 19, 164, 178, 198, 141, 47, 52, 125, 220, 172, 129, 137, 81, 221, 75, 4, 224, 184, 11, 147, 206, 164, 85, 181, 217, 75, 0, 114, 74, 2, 17, 0, 0, 0, 24, 77, 161, 106, 58, 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