Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cec9cb4caa0ab3c720c8d22e261f8a265fff374f6186c95a9a9c4760a013db79

Tx prefix hash: 9998a08a6248e91c476a80851c9d88be21a8bac48ee9c726552ddc0eee7600b3
Tx public key: 5c490731d967f96af84054a2aa146f97d63919dfefc72309d8180d579a2dfc8e
Timestamp: 1708988919 Timestamp [UCT]: 2024-02-26 23:08:39 Age [y:d:h:m:s]: 01:039:22:52:29
Block: 966276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289548 RingCT/type: yes/0
Extra: 015c490731d967f96af84054a2aa146f97d63919dfefc72309d8180d579a2dfc8e02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7ca484c1064f7e9913f52afd9fee4af056f1a7c328911d7fa87e3585ddda89b 0.600000000000 1426033 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": 966286, "vin": [ { "gen": { "height": 966276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7ca484c1064f7e9913f52afd9fee4af056f1a7c328911d7fa87e3585ddda89b" } } ], "extra": [ 1, 92, 73, 7, 49, 217, 103, 249, 106, 248, 64, 84, 162, 170, 20, 111, 151, 214, 57, 25, 223, 239, 199, 35, 9, 216, 24, 13, 87, 154, 45, 252, 142, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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