Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00c76b14dd20fa40e09b7f9cbce7b61da135ef5313153f67ffdc4488d2b06adc

Tx prefix hash: c23d2692774516e5e84d8aa0bbb4dbd98c42f8a68c8c7af8a51bf369b315306c
Tx public key: 6be0fde4809a45ddaaa878f82ad0d34ae5ddcd92f145d39cbc7e72134aaa3c20
Timestamp: 1710410592 Timestamp [UCT]: 2024-03-14 10:03:12 Age [y:d:h:m:s]: 01:011:05:58:45
Block: 978074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268998 RingCT/type: yes/0
Extra: 016be0fde4809a45ddaaa878f82ad0d34ae5ddcd92f145d39cbc7e72134aaa3c200211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76d8e4f783e68a62c58b3ba002a449b7c58ccdab32ae78ce6b46d3a6f88cec18 0.600000000000 1438091 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": 978084, "vin": [ { "gen": { "height": 978074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76d8e4f783e68a62c58b3ba002a449b7c58ccdab32ae78ce6b46d3a6f88cec18" } } ], "extra": [ 1, 107, 224, 253, 228, 128, 154, 69, 221, 170, 168, 120, 248, 42, 208, 211, 74, 229, 221, 205, 146, 241, 69, 211, 156, 188, 126, 114, 19, 74, 170, 60, 32, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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