Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71abe33db1627871bc88482a30273cbf0b383e8789cdb64e1f936c7ae6e342a4

Tx prefix hash: 881b96f93ee7ca01245ba4b9d55b2769e9796cfaee574900a7a71f0519c17177
Tx public key: 733fc5e2baf27e36e48bcbf8fb16e05a62cd7437d5a9f41796607ad2dbc6a7d9
Timestamp: 1749611704 Timestamp [UCT]: 2025-06-11 03:15:04 Age [y:d:h:m:s]: 00:152:16:29:40
Block: 1302486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106811 RingCT/type: yes/0
Extra: 01733fc5e2baf27e36e48bcbf8fb16e05a62cd7437d5a9f41796607ad2dbc6a7d902110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bafd0d3fbda57877921d9f830bb5c67beff566c23f4e18fe9a6551f4d11ba03f 0.600000000000 1790057 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": 1302496, "vin": [ { "gen": { "height": 1302486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bafd0d3fbda57877921d9f830bb5c67beff566c23f4e18fe9a6551f4d11ba03f" } } ], "extra": [ 1, 115, 63, 197, 226, 186, 242, 126, 54, 228, 139, 203, 248, 251, 22, 224, 90, 98, 205, 116, 55, 213, 169, 244, 23, 150, 96, 122, 210, 219, 198, 167, 217, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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