Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0eddccfb86dd5f8f3c288c20f78ccea6dfd8eeeafe7dd25c6e5a95c134aa4c6

Tx prefix hash: aa7597531d22696e64f7147bbcd5d894e61b68a6dd435df93acb0e843fdc362c
Tx public key: 298f0f0ada2066fbf13cc4e60e91643d088b4b5d3b5e5df41b41753dcaaacd92
Timestamp: 1731293000 Timestamp [UCT]: 2024-11-11 02:43:20 Age [y:d:h:m:s]: 00:135:05:43:27
Block: 1151097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96454 RingCT/type: yes/0
Extra: 01298f0f0ada2066fbf13cc4e60e91643d088b4b5d3b5e5df41b41753dcaaacd920211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d45ef8ffd3980fb73edbd8e2bc043bc3aa203a034349ed65059eeacaf83e872 0.600000000000 1636556 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": 1151107, "vin": [ { "gen": { "height": 1151097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d45ef8ffd3980fb73edbd8e2bc043bc3aa203a034349ed65059eeacaf83e872" } } ], "extra": [ 1, 41, 143, 15, 10, 218, 32, 102, 251, 241, 60, 196, 230, 14, 145, 100, 61, 8, 139, 75, 93, 59, 94, 93, 244, 27, 65, 117, 61, 202, 170, 205, 146, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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