Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5eb488583d840513c9e508d6c0d8454a1920837f67ad8166947bcc02bcc97a4a

Tx prefix hash: 2f45c4e1da3ce99684935de23aae288566df9e7818a65353eef55757b19c1b55
Tx public key: 42cb1093f0e8d7b8563eb416cd77dcdd33ee7b176c0dcf681a0cf52ff1325205
Timestamp: 1702131830 Timestamp [UCT]: 2023-12-09 14:23:50 Age [y:d:h:m:s]: 01:159:05:23:27
Block: 909416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374967 RingCT/type: yes/0
Extra: 0142cb1093f0e8d7b8563eb416cd77dcdd33ee7b176c0dcf681a0cf52ff13252050211000000014b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cf186bd05dd58d61f5b4081b127e8b4636441581f34cb2ee9ebc0ca2b722d5b 0.600000000000 1366503 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": 909426, "vin": [ { "gen": { "height": 909416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cf186bd05dd58d61f5b4081b127e8b4636441581f34cb2ee9ebc0ca2b722d5b" } } ], "extra": [ 1, 66, 203, 16, 147, 240, 232, 215, 184, 86, 62, 180, 22, 205, 119, 220, 221, 51, 238, 123, 23, 108, 13, 207, 104, 26, 12, 245, 47, 241, 50, 82, 5, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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