Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b6fbb357012b3d016552b5e72ad2f7464c5b1f2aecc169df9f59f0e0ca56f08

Tx prefix hash: 4549001149e1616ead8898b3dfd5bb5603f24d58e781a6962469a35f70ba36c1
Tx public key: 1f365da53910e4194b3d0ff7d2b40f1e1e55b4187fb9076c75309f40a3883ac3
Timestamp: 1702132520 Timestamp [UCT]: 2023-12-09 14:35:20 Age [y:d:h:m:s]: 01:101:09:59:23
Block: 909426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333636 RingCT/type: yes/0
Extra: 011f365da53910e4194b3d0ff7d2b40f1e1e55b4187fb9076c75309f40a3883ac302110000000e33af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8006ce2f458bae5e876824d5869b6a37170d5c46a3a8f7df28ed71bfe2d9f817 0.600000000000 1366513 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": 909436, "vin": [ { "gen": { "height": 909426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8006ce2f458bae5e876824d5869b6a37170d5c46a3a8f7df28ed71bfe2d9f817" } } ], "extra": [ 1, 31, 54, 93, 165, 57, 16, 228, 25, 75, 61, 15, 247, 210, 180, 15, 30, 30, 85, 180, 24, 127, 185, 7, 108, 117, 48, 159, 64, 163, 136, 58, 195, 2, 17, 0, 0, 0, 14, 51, 175, 153, 244, 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