Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b9f8f7887a0ba4cfd0c1e363f2d17f3319cb3768572134984379cf81d1d2ee6

Tx prefix hash: adb37cc4426ba99a1d754512b513558140f45c502a0df212ebaee411621cef21
Tx public key: a0ee414f295bc311bab7c2a4aa5663fd67c4e7949c6f109c5323d282408180a6
Timestamp: 1729785174 Timestamp [UCT]: 2024-10-24 15:52:54 Age [y:d:h:m:s]: 00:180:22:01:07
Block: 1138641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129114 RingCT/type: yes/0
Extra: 01a0ee414f295bc311bab7c2a4aa5663fd67c4e7949c6f109c5323d282408180a60211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94880dbae65988f03acb459823fa20ff477ab1ff99470c55b9b61cd056fd23e7 0.600000000000 1622336 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": 1138651, "vin": [ { "gen": { "height": 1138641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94880dbae65988f03acb459823fa20ff477ab1ff99470c55b9b61cd056fd23e7" } } ], "extra": [ 1, 160, 238, 65, 79, 41, 91, 195, 17, 186, 183, 194, 164, 170, 86, 99, 253, 103, 196, 231, 148, 156, 111, 16, 156, 83, 35, 210, 130, 64, 129, 128, 166, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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