Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51f5c11edcf2757d1b6b2af187d3fd5773bd3278d64df14001cd2f02609cec80

Tx prefix hash: 5b11b5d439d3848f1fbe6ae5c3377ead5ecf7110672b2bc3a456458955d3328c
Tx public key: 65040bea9cd086b5d1e2e99d8d7f86e2eeaadfbc65a8f0795e2d85b62d66c20b
Timestamp: 1658516943 Timestamp [UCT]: 2022-07-22 19:09:03 Age [y:d:h:m:s]: 02:178:00:38:00
Block: 549468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 648629 RingCT/type: yes/0
Extra: 0165040bea9cd086b5d1e2e99d8d7f86e2eeaadfbc65a8f0795e2d85b62d66c20b0211000000125eb576c5000000000000000000

1 output(s) for total of 9.276508653000 dcy

stealth address amount amount idx
00: a8532c5cc5c4607a4441e0cd67d6915b04f791ee84b98d1324ea7363a1c92ca1 9.276508653000 980837 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": 549478, "vin": [ { "gen": { "height": 549468 } } ], "vout": [ { "amount": 9276508653, "target": { "key": "a8532c5cc5c4607a4441e0cd67d6915b04f791ee84b98d1324ea7363a1c92ca1" } } ], "extra": [ 1, 101, 4, 11, 234, 156, 208, 134, 181, 209, 226, 233, 157, 141, 127, 134, 226, 238, 170, 223, 188, 101, 168, 240, 121, 94, 45, 133, 182, 45, 102, 194, 11, 2, 17, 0, 0, 0, 18, 94, 181, 118, 197, 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