Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03e2c48e2330b404f33b19a016a58b2665b9b0a227af5f76c31f513d7a72bfd0

Tx prefix hash: 6e59037b6922bca8fe158e1a22ebbe1af4e9d413e279fcb424ccd8d6c5c2b6af
Tx public key: 0f5d2440f23f9c10017dacdf8ca9eb255096b887802331f610e1f76d4d5df822
Timestamp: 1579037347 Timestamp [UCT]: 2020-01-14 21:29:07 Age [y:d:h:m:s]: 04:349:22:09:56
Block: 45606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1139609 RingCT/type: yes/0
Extra: 010f5d2440f23f9c10017dacdf8ca9eb255096b887802331f610e1f76d4d5df82202110000006a49b77a3d000000000000000000

1 output(s) for total of 433.400321821000 dcy

stealth address amount amount idx
00: 87a517a1d9be103fa68476c6ffa10135d778ef36762c2d750d737f4c7318554e 433.400321821000 83425 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": 45616, "vin": [ { "gen": { "height": 45606 } } ], "vout": [ { "amount": 433400321821, "target": { "key": "87a517a1d9be103fa68476c6ffa10135d778ef36762c2d750d737f4c7318554e" } } ], "extra": [ 1, 15, 93, 36, 64, 242, 63, 156, 16, 1, 125, 172, 223, 140, 169, 235, 37, 80, 150, 184, 135, 128, 35, 49, 246, 16, 225, 247, 109, 77, 93, 248, 34, 2, 17, 0, 0, 0, 106, 73, 183, 122, 61, 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