Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b775e36e088a7a303de2156506c1fb624568a8e9c60cc129021578b4445265e7

Tx prefix hash: f36368b6a7d6c6cadf40074950d85400b7d68f407e2ab0d3c43af5d0dff29472
Tx public key: 8aebc18be3572c1c83e12fae3a18e617fad40a0b4780a6a98ba2337b246c6da0
Timestamp: 1741665068 Timestamp [UCT]: 2025-03-11 03:51:08 Age [y:d:h:m:s]: 00:255:20:34:49
Block: 1236709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180598 RingCT/type: yes/0
Extra: 018aebc18be3572c1c83e12fae3a18e617fad40a0b4780a6a98ba2337b246c6da0021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebbd93ae9bb9f33a53e9f0b2ec3fe137a478c9ac406c1bb0df5c2d8d6fb3a773 0.600000000000 1723660 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": 1236719, "vin": [ { "gen": { "height": 1236709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebbd93ae9bb9f33a53e9f0b2ec3fe137a478c9ac406c1bb0df5c2d8d6fb3a773" } } ], "extra": [ 1, 138, 235, 193, 139, 227, 87, 44, 28, 131, 225, 47, 174, 58, 24, 230, 23, 250, 212, 10, 11, 71, 128, 166, 169, 139, 162, 51, 123, 36, 108, 109, 160, 2, 17, 0, 0, 0, 5, 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