Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80207630f80dc982fdba36bb63e2fbd3d2cf56808c76ecbea8f1a21d97e0cddb

Tx prefix hash: 33274c84c11a73e1ab46286efd123f66f380514bd4087a7f26befed3cc0692f6
Tx public key: a95c6ced7e32bd7489c6ca1ba0600d7ee5252d2ad729e57ede43b8db42df893f
Timestamp: 1652609619 Timestamp [UCT]: 2022-05-15 10:13:39 Age [y:d:h:m:s]: 03:170:10:10:33
Block: 501446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 900723 RingCT/type: yes/0
Extra: 01a95c6ced7e32bd7489c6ca1ba0600d7ee5252d2ad729e57ede43b8db42df893f02110000001575e3f0e9000000000000000000

1 output(s) for total of 13.381396683000 dcy

stealth address amount amount idx
00: 17ae5970a188995513ee2455d29efd97f9c641f4df4b9170fa213de105bed3f8 13.381396683000 926113 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": 501456, "vin": [ { "gen": { "height": 501446 } } ], "vout": [ { "amount": 13381396683, "target": { "key": "17ae5970a188995513ee2455d29efd97f9c641f4df4b9170fa213de105bed3f8" } } ], "extra": [ 1, 169, 92, 108, 237, 126, 50, 189, 116, 137, 198, 202, 27, 160, 96, 13, 126, 229, 37, 45, 42, 215, 41, 229, 126, 222, 67, 184, 219, 66, 223, 137, 63, 2, 17, 0, 0, 0, 21, 117, 227, 240, 233, 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