Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30e3b49af350c89a8e9f79f050c023470365e6e429896d58689c9ce5d0105c0f

Tx prefix hash: f19deed3121c45d1e59df72c5baf73ee3a061d97c5aad55d4ecfdf936387c708
Tx public key: abd07acf2f49ee2e0be886ee683204650c5a2224a0e725b06d1f404e19ea6c06
Timestamp: 1725773188 Timestamp [UCT]: 2024-09-08 05:26:28 Age [y:d:h:m:s]: 00:279:04:46:13
Block: 1105419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199358 RingCT/type: yes/0
Extra: 01abd07acf2f49ee2e0be886ee683204650c5a2224a0e725b06d1f404e19ea6c0602110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd0abd020166ac4ca22a75bad9a15333c457bb5337d4187b37b9d5a72d246ed0 0.600000000000 1582762 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": 1105429, "vin": [ { "gen": { "height": 1105419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd0abd020166ac4ca22a75bad9a15333c457bb5337d4187b37b9d5a72d246ed0" } } ], "extra": [ 1, 171, 208, 122, 207, 47, 73, 238, 46, 11, 232, 134, 238, 104, 50, 4, 101, 12, 90, 34, 36, 160, 231, 37, 176, 109, 31, 64, 78, 25, 234, 108, 6, 2, 17, 0, 0, 0, 7, 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