Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3539d709be4d61778e17ecea7aea63b2c89b43474fd44807f55036dbabd6ac5

Tx prefix hash: 3d4094c069fce7fbd1703e8fc31ce02b6b0ed2fdebdcc40fa24722eb25a95815
Tx public key: 803128c5d191bba5e9dafaddf3c01f0fdfea7f132323d9091be4fab3fa99a4b1
Timestamp: 1750124511 Timestamp [UCT]: 2025-06-17 01:41:51 Age [y:d:h:m:s]: 00:154:05:54:35
Block: 1306634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108025 RingCT/type: yes/0
Extra: 01803128c5d191bba5e9dafaddf3c01f0fdfea7f132323d9091be4fab3fa99a4b1021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0365051f766cd42d3be73cb40c7a24a48b05ce12402bbc1a8f0bac1cf0832b96 0.600000000000 1794241 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": 1306644, "vin": [ { "gen": { "height": 1306634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0365051f766cd42d3be73cb40c7a24a48b05ce12402bbc1a8f0bac1cf0832b96" } } ], "extra": [ 1, 128, 49, 40, 197, 209, 145, 187, 165, 233, 218, 250, 221, 243, 192, 31, 15, 223, 234, 127, 19, 35, 35, 217, 9, 27, 228, 250, 179, 250, 153, 164, 177, 2, 17, 0, 0, 0, 1, 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