Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3d22c4bc5fbe3d0de6e7a7bc04e46ec59953c4303d1c5ff675ffd89da1b2f7c

Tx prefix hash: a4ea1375012bd4be228009d3a0402404f9273d402b9054ba88899dc5f3c9fbdb
Tx public key: 291e6b859f18af64b5796cf2b48ef6e172f7a79689ffa47a39a7a7de7fdabbf0
Timestamp: 1723024779 Timestamp [UCT]: 2024-08-07 09:59:39 Age [y:d:h:m:s]: 00:200:00:18:42
Block: 1082636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142799 RingCT/type: yes/0
Extra: 01291e6b859f18af64b5796cf2b48ef6e172f7a79689ffa47a39a7a7de7fdabbf0021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04739544cef2a75cb529d3227d544e2131898ed61574e823772bb4355c87f0f0 0.600000000000 1556465 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": 1082646, "vin": [ { "gen": { "height": 1082636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04739544cef2a75cb529d3227d544e2131898ed61574e823772bb4355c87f0f0" } } ], "extra": [ 1, 41, 30, 107, 133, 159, 24, 175, 100, 181, 121, 108, 242, 180, 142, 246, 225, 114, 247, 167, 150, 137, 255, 164, 122, 57, 167, 167, 222, 127, 218, 187, 240, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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