Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cee5bbbf28755c3055b86933c645492594e3f5e2f7f3ba026d144ca8ca47073

Tx prefix hash: 6e157ec93654140b162760476219c8677b92411bd0605790e35b2e05185c53fc
Tx public key: 565f336cb55692b14ed0224a6adc1bbd7a6fa57e6d15f752895be7d88f2975b1
Timestamp: 1718573885 Timestamp [UCT]: 2024-06-16 21:38:05 Age [y:d:h:m:s]: 00:222:06:30:24
Block: 1045744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159000 RingCT/type: yes/0
Extra: 01565f336cb55692b14ed0224a6adc1bbd7a6fa57e6d15f752895be7d88f2975b10211000000028fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9b43e4ffb41a998f46178c2b7c9d7c64c06f1808ed82c087e4a2cbb5491a247 0.600000000000 1515407 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": 1045754, "vin": [ { "gen": { "height": 1045744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9b43e4ffb41a998f46178c2b7c9d7c64c06f1808ed82c087e4a2cbb5491a247" } } ], "extra": [ 1, 86, 95, 51, 108, 181, 86, 146, 177, 78, 208, 34, 74, 106, 220, 27, 189, 122, 111, 165, 126, 109, 21, 247, 82, 137, 91, 231, 216, 143, 41, 117, 177, 2, 17, 0, 0, 0, 2, 143, 218, 155, 45, 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