Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b04dc7299906eba06e349a20cb05d8b741ed71a23f08a1713a1dd6cede65bb62

Tx prefix hash: 0f3722b194214cf33c405842f106983222fa2ad865f04e07507f4366f903b1e9
Tx public key: 24f09630a42d64f8c362bbf8f62b1be5ca5d2e047916421f987b81eb5d5bc1f9
Timestamp: 1746412855 Timestamp [UCT]: 2025-05-05 02:40:55 Age [y:d:h:m:s]: 00:200:12:49:23
Block: 1276000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141033 RingCT/type: yes/0
Extra: 0124f09630a42d64f8c362bbf8f62b1be5ca5d2e047916421f987b81eb5d5bc1f90211000000061f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01f8caff0edd7988c98f995cb4dd50aaefa463b405165d3c745b0848b63487a8 0.600000000000 1763315 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": 1276010, "vin": [ { "gen": { "height": 1276000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01f8caff0edd7988c98f995cb4dd50aaefa463b405165d3c745b0848b63487a8" } } ], "extra": [ 1, 36, 240, 150, 48, 164, 45, 100, 248, 195, 98, 187, 248, 246, 43, 27, 229, 202, 93, 46, 4, 121, 22, 66, 31, 152, 123, 129, 235, 93, 91, 193, 249, 2, 17, 0, 0, 0, 6, 31, 144, 81, 122, 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