Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2b0ead0c8dc40874b0bf0b0ffc9edc0ad23166c9c278075b8bcd09d85645ae5

Tx prefix hash: 1d1bae69bbcb8e031d1dcd9893bf23e81e0e514045c764e33537e8a848680adc
Tx public key: c33849c17b019376e842d0dc395d631d092d2dd18bd17c3956749dd5b678d354
Timestamp: 1751321741 Timestamp [UCT]: 2025-06-30 22:15:41 Age [y:d:h:m:s]: 00:211:01:50:19
Block: 1316131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148959 RingCT/type: yes/0
Extra: 01c33849c17b019376e842d0dc395d631d092d2dd18bd17c3956749dd5b678d354021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd801ebecc1a1d31d476be5ea72014ee48ba45400912d15db4c97c07caf86f4c 0.600000000000 1803788 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": 1316141, "vin": [ { "gen": { "height": 1316131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd801ebecc1a1d31d476be5ea72014ee48ba45400912d15db4c97c07caf86f4c" } } ], "extra": [ 1, 195, 56, 73, 193, 123, 1, 147, 118, 232, 66, 208, 220, 57, 93, 99, 29, 9, 45, 45, 209, 139, 209, 124, 57, 86, 116, 157, 213, 182, 120, 211, 84, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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