Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f91ad928cadce2b999ac36a4bc9d0229557d0947427384a492a07b26839bbecd

Tx prefix hash: dd2c9bc60b47403f580a776c4837349a687c8c4a6ad3c37fddc73e8fc7acaa7b
Tx public key: 459c7efb3c11e7a2ab1ae4f9f504842fb47c568b010550d963d524ae303d8368
Timestamp: 1720782327 Timestamp [UCT]: 2024-07-12 11:05:27 Age [y:d:h:m:s]: 00:248:01:45:54
Block: 1064052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177231 RingCT/type: yes/0
Extra: 01459c7efb3c11e7a2ab1ae4f9f504842fb47c568b010550d963d524ae303d836802110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdd57357010901d63d5d55f88d5c988cbd60d6951fbd8965658ec95d39ffa927 0.600000000000 1534575 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": 1064062, "vin": [ { "gen": { "height": 1064052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdd57357010901d63d5d55f88d5c988cbd60d6951fbd8965658ec95d39ffa927" } } ], "extra": [ 1, 69, 156, 126, 251, 60, 17, 231, 162, 171, 26, 228, 249, 245, 4, 132, 47, 180, 124, 86, 139, 1, 5, 80, 217, 99, 213, 36, 174, 48, 61, 131, 104, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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