Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f48448c819107b976fd86bd132f1a6563e182b32b6927a44ac935b42b88428c

Tx prefix hash: 7a5ca9691a2f6e951161c960421345edc0f4f3dd278c93fa5066dadbd638f3e1
Tx public key: 2e2dac38bf79a0b6208caaf83f141c445351d9104e7f4a03a51ff310618082d1
Timestamp: 1722731182 Timestamp [UCT]: 2024-08-04 00:26:22 Age [y:d:h:m:s]: 01:095:00:58:38
Block: 1080197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326396 RingCT/type: yes/0
Extra: 012e2dac38bf79a0b6208caaf83f141c445351d9104e7f4a03a51ff310618082d1021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 939f207f21dc092e22aadfaa7b5f3815aceab9e79715d0d213a940cf9cab4da7 0.600000000000 1553466 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": 1080207, "vin": [ { "gen": { "height": 1080197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "939f207f21dc092e22aadfaa7b5f3815aceab9e79715d0d213a940cf9cab4da7" } } ], "extra": [ 1, 46, 45, 172, 56, 191, 121, 160, 182, 32, 140, 170, 248, 63, 20, 28, 68, 83, 81, 217, 16, 78, 127, 74, 3, 165, 31, 243, 16, 97, 128, 130, 209, 2, 17, 0, 0, 0, 5, 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