Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2cc7232cef2ebe8faaf29f644485841e6c9c9dd6cf3f2f1108bbe72e2e0bc2b

Tx prefix hash: 87e0e905a06304f43b92d29318abea883db4dcaf28e352d042858ae2b23f3960
Tx public key: 726222eb243c1ab38c9db96d91d8a85002bb538efc81e0e9c76756da4fde926c
Timestamp: 1744959513 Timestamp [UCT]: 2025-04-18 06:58:33 Age [y:d:h:m:s]: 00:256:12:53:12
Block: 1263975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181126 RingCT/type: yes/0
Extra: 01726222eb243c1ab38c9db96d91d8a85002bb538efc81e0e9c76756da4fde926c021100000007dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3f995490a0e98298c5c2e9adbc6b8df05535bdbf1ba5e40948971a33abf56f9 0.600000000000 1751168 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": 1263985, "vin": [ { "gen": { "height": 1263975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3f995490a0e98298c5c2e9adbc6b8df05535bdbf1ba5e40948971a33abf56f9" } } ], "extra": [ 1, 114, 98, 34, 235, 36, 60, 26, 179, 140, 157, 185, 109, 145, 216, 168, 80, 2, 187, 83, 142, 252, 129, 224, 233, 199, 103, 86, 218, 79, 222, 146, 108, 2, 17, 0, 0, 0, 7, 219, 181, 113, 193, 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