Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 590711b303e03a54a19552ac4025fe28a1aa51a169c14d1c32149128ed9b261d

Tx prefix hash: 7f629efe57fd6e15720845ad557988efa2af0b48e2f44678f4854db5b7080e9d
Tx public key: 72a21657fccecca10b651f2d8aa5fbeaab1ee2e6e86e4452cc9bf326fd37dabd
Timestamp: 1738901095 Timestamp [UCT]: 2025-02-07 04:04:55 Age [y:d:h:m:s]: 00:287:04:55:29
Block: 1213833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203000 RingCT/type: yes/0
Extra: 0172a21657fccecca10b651f2d8aa5fbeaab1ee2e6e86e4452cc9bf326fd37dabd021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f4214b9d9bf616e62c2d1f410d8f722bf35ad25a6117f28797b7e041e48c2fe 0.600000000000 1700614 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": 1213843, "vin": [ { "gen": { "height": 1213833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f4214b9d9bf616e62c2d1f410d8f722bf35ad25a6117f28797b7e041e48c2fe" } } ], "extra": [ 1, 114, 162, 22, 87, 252, 206, 204, 161, 11, 101, 31, 45, 138, 165, 251, 234, 171, 30, 226, 230, 232, 110, 68, 82, 204, 155, 243, 38, 253, 55, 218, 189, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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