Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e7600b70b4e4bc4f678ea3ce2d41122484b8ee35aa27013b2e5bafcf8f06ff3

Tx prefix hash: f5747b21de4ef66005634aead8733a1819fc340e89c74d9ed409743cdd617b8c
Tx public key: 1a389bf33ae0cf744c9e142f7d0494f85eec03cf0c344415c3ab9a0d07ce342e
Timestamp: 1714139408 Timestamp [UCT]: 2024-04-26 13:50:08 Age [y:d:h:m:s]: 00:202:12:58:59
Block: 1008965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144981 RingCT/type: yes/0
Extra: 011a389bf33ae0cf744c9e142f7d0494f85eec03cf0c344415c3ab9a0d07ce342e02110000000118ec9060000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab7a8b79857b5db6dc0fad76f2bd3980f54a73c09c39e6d3b9762dbe14ae8e00 0.600000000000 1470493 of 15

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": 1008975, "vin": [ { "gen": { "height": 1008965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab7a8b79857b5db6dc0fad76f2bd3980f54a73c09c39e6d3b9762dbe14ae8e00" } } ], "extra": [ 1, 26, 56, 155, 243, 58, 224, 207, 116, 76, 158, 20, 47, 125, 4, 148, 248, 94, 236, 3, 207, 12, 52, 68, 21, 195, 171, 154, 13, 7, 206, 52, 46, 2, 17, 0, 0, 0, 1, 24, 236, 144, 96, 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