Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91e7555a621f49777d099d3aa507d2a8d63dd84b0dd81e43a6d086fe8de12fd4

Tx prefix hash: 84f066788c4e6536a6198932ffa632fb644c7f4c096111dc29dbd4eac7826b06
Tx public key: dab531b6674df522aef14114d12cdf9747ccddfcac0aabdcfe40fb67157916d9
Timestamp: 1694046460 Timestamp [UCT]: 2023-09-07 00:27:40 Age [y:d:h:m:s]: 01:112:14:08:42
Block: 842567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341792 RingCT/type: yes/0
Extra: 01dab531b6674df522aef14114d12cdf9747ccddfcac0aabdcfe40fb67157916d902110000000475e3f0e9000000000000000000

1 output(s) for total of 0.991347305000 dcy

stealth address amount amount idx
00: 34d0cb98b0135d94971702e04cda89f2d8221e566e41a22ac16c789e16c066aa 0.991347305000 1295699 of 0

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": 842577, "vin": [ { "gen": { "height": 842567 } } ], "vout": [ { "amount": 991347305, "target": { "key": "34d0cb98b0135d94971702e04cda89f2d8221e566e41a22ac16c789e16c066aa" } } ], "extra": [ 1, 218, 181, 49, 182, 103, 77, 245, 34, 174, 241, 65, 20, 209, 44, 223, 151, 71, 204, 221, 252, 172, 10, 171, 220, 254, 64, 251, 103, 21, 121, 22, 217, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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