Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 929e2f9b5df6181056ced8d0de97fd3321372639898073e535556b6697daf279

Tx prefix hash: c26c91e4194c665a90aaab8eb5c2e4d7c2842d0e55a97a8e7f7fd3711c08cbc5
Tx public key: 407038b26ff9723769ea29986b8f7b5f8144350a10d6aacbe194f59a5bd27781
Timestamp: 1722045846 Timestamp [UCT]: 2024-07-27 02:04:06 Age [y:d:h:m:s]: 00:294:09:18:59
Block: 1074510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210339 RingCT/type: yes/0
Extra: 01407038b26ff9723769ea29986b8f7b5f8144350a10d6aacbe194f59a5bd27781021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08b690f1d1f81cb2d2ca834acb2933f177559d71fbae38084eb5af9b527b1503 0.600000000000 1547023 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": 1074520, "vin": [ { "gen": { "height": 1074510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08b690f1d1f81cb2d2ca834acb2933f177559d71fbae38084eb5af9b527b1503" } } ], "extra": [ 1, 64, 112, 56, 178, 111, 249, 114, 55, 105, 234, 41, 152, 107, 143, 123, 95, 129, 68, 53, 10, 16, 214, 170, 203, 225, 148, 245, 154, 91, 210, 119, 129, 2, 17, 0, 0, 0, 1, 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