Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 254e95716e8d1864eadfa40b741f4b62ebfd33e2bff0f38ea489a9b401ce1517

Tx prefix hash: a168fd627b2e7bfb91dcb8249a45dbda6fe6635124fe73253d714030b80bbf6e
Tx public key: 2872cc11a959b263afe3d0b2f34cbb2e4286df21a12cceaee1e26c55ef361015
Timestamp: 1659325890 Timestamp [UCT]: 2022-08-01 03:51:30 Age [y:d:h:m:s]: 02:101:16:58:03
Block: 556140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594064 RingCT/type: yes/0
Extra: 012872cc11a959b263afe3d0b2f34cbb2e4286df21a12cceaee1e26c55ef361015021100000001ec6d1a1a000000000000000000

1 output(s) for total of 8.816118897000 dcy

stealth address amount amount idx
00: d8722e723c785a932fbdfeb51a5551ad5d3643c16c5d8d2b9f36d9b0c9e75cd6 8.816118897000 988066 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": 556150, "vin": [ { "gen": { "height": 556140 } } ], "vout": [ { "amount": 8816118897, "target": { "key": "d8722e723c785a932fbdfeb51a5551ad5d3643c16c5d8d2b9f36d9b0c9e75cd6" } } ], "extra": [ 1, 40, 114, 204, 17, 169, 89, 178, 99, 175, 227, 208, 178, 243, 76, 187, 46, 66, 134, 223, 33, 161, 44, 206, 174, 225, 226, 108, 85, 239, 54, 16, 21, 2, 17, 0, 0, 0, 1, 236, 109, 26, 26, 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