Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cefb95d16e68c54c561b2de218e886c9da98027504352395f4a7d81624242db

Tx prefix hash: 09a14897c7169fb4f4f80fde7041634589127ae801daf50b4a2e60a68b98bfa0
Tx public key: 928ec49b2c60e4ab60a61d940f4af55f8cd550c424f710bfb66c855a992186c6
Timestamp: 1720806009 Timestamp [UCT]: 2024-07-12 17:40:09 Age [y:d:h:m:s]: 00:135:01:12:54
Block: 1064250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96623 RingCT/type: yes/0
Extra: 01928ec49b2c60e4ab60a61d940f4af55f8cd550c424f710bfb66c855a992186c602110000001391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dedd57a87ff3167fb94373b944a2f07520d3f75bb2e6a3bbbb0204521ada7ea 0.600000000000 1534773 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": 1064260, "vin": [ { "gen": { "height": 1064250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dedd57a87ff3167fb94373b944a2f07520d3f75bb2e6a3bbbb0204521ada7ea" } } ], "extra": [ 1, 146, 142, 196, 155, 44, 96, 228, 171, 96, 166, 29, 148, 15, 74, 245, 95, 140, 213, 80, 196, 36, 247, 16, 191, 182, 108, 133, 90, 153, 33, 134, 198, 2, 17, 0, 0, 0, 19, 145, 225, 60, 4, 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