Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b05bc1a09a624ac3b2704193dc4586391a7916abc44736ce66bc98d1319ae55

Tx prefix hash: 1b4f23a8a3af9315b57302b4bac45fa48531403a6d2567a1bb346c6158d5442f
Tx public key: b3ed2ef8cbb891dfad1d842edc868cf633be7213117771784e7fcd5b09d8e17e
Timestamp: 1578756179 Timestamp [UCT]: 2020-01-11 15:22:59 Age [y:d:h:m:s]: 04:320:03:19:53
Block: 43306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118280 RingCT/type: yes/0
Extra: 01b3ed2ef8cbb891dfad1d842edc868cf633be7213117771784e7fcd5b09d8e17e0211000000134943cd9f000000000000000000

1 output(s) for total of 441.072608056000 dcy

stealth address amount amount idx
00: 10c06235df4a24488b1a1f177d6ae025beae362870f7a40d45b673c74a20df6c 441.072608056000 78377 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": 43316, "vin": [ { "gen": { "height": 43306 } } ], "vout": [ { "amount": 441072608056, "target": { "key": "10c06235df4a24488b1a1f177d6ae025beae362870f7a40d45b673c74a20df6c" } } ], "extra": [ 1, 179, 237, 46, 248, 203, 184, 145, 223, 173, 29, 132, 46, 220, 134, 140, 246, 51, 190, 114, 19, 17, 119, 113, 120, 78, 127, 205, 91, 9, 216, 225, 126, 2, 17, 0, 0, 0, 19, 73, 67, 205, 159, 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