Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38723d106d484972d4cc694db163b004fd4b4f281aa347fad4b4c8aefd768d78

Tx prefix hash: 40940df71c930486572d3bd1c87bda722f3907e81822cf9332d7dff708082f4c
Tx public key: 76c82adfbb4ea929c7fbacabfc8e4f19b75a08601f1eafab3648534ce800cb82
Timestamp: 1633113046 Timestamp [UCT]: 2021-10-01 18:30:46 Age [y:d:h:m:s]: 03:089:22:33:35
Block: 344650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 841211 RingCT/type: yes/0
Extra: 0176c82adfbb4ea929c7fbacabfc8e4f19b75a08601f1eafab3648534ce800cb820211000000015d7cc334000000000000000000

1 output(s) for total of 44.262088978000 dcy

stealth address amount amount idx
00: f077a7f918277391ce45f8bed6ac1a0a8822965c7f868461ff02f41352b556d0 44.262088978000 707110 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": 344660, "vin": [ { "gen": { "height": 344650 } } ], "vout": [ { "amount": 44262088978, "target": { "key": "f077a7f918277391ce45f8bed6ac1a0a8822965c7f868461ff02f41352b556d0" } } ], "extra": [ 1, 118, 200, 42, 223, 187, 78, 169, 41, 199, 251, 172, 171, 252, 142, 79, 25, 183, 90, 8, 96, 31, 30, 175, 171, 54, 72, 83, 76, 232, 0, 203, 130, 2, 17, 0, 0, 0, 1, 93, 124, 195, 52, 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