Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b0a9861ffeaaea9c30c5ea16b4003a2f11750c803a339953bb9d0f38e53bf9f

Tx prefix hash: 21b5612eb2062d95aa330ca91af6b1d602821e29ba9ccee712819cf1bffda370
Tx public key: 37bb402e7e8aff2583affa5c71d99cdee98b2daa17e2541bdfca400d0f48f687
Timestamp: 1581971799 Timestamp [UCT]: 2020-02-17 20:36:39 Age [y:d:h:m:s]: 05:016:10:50:14
Block: 67031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1164768 RingCT/type: yes/0
Extra: 0137bb402e7e8aff2583affa5c71d99cdee98b2daa17e2541bdfca400d0f48f6870211000000194ac5aa02000000000000000000

1 output(s) for total of 368.043607676000 dcy

stealth address amount amount idx
00: 7902888d232fe666914770b95359c4d0a80c6bd656bc57749d730c117a6ba712 368.043607676000 123461 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": 67041, "vin": [ { "gen": { "height": 67031 } } ], "vout": [ { "amount": 368043607676, "target": { "key": "7902888d232fe666914770b95359c4d0a80c6bd656bc57749d730c117a6ba712" } } ], "extra": [ 1, 55, 187, 64, 46, 126, 138, 255, 37, 131, 175, 250, 92, 113, 217, 156, 222, 233, 139, 45, 170, 23, 226, 84, 27, 223, 202, 64, 13, 15, 72, 246, 135, 2, 17, 0, 0, 0, 25, 74, 197, 170, 2, 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