Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f60032f9c8acfd218b27f6a3585868334e0e021dc7ab842dc04d3143a8e9653

Tx prefix hash: e92ad90c97281bc9c41943a5cfc98e19c2748c359888a2b512c6a7078b386bd9
Tx public key: cb9a7675acb49ebc2251dcc267303e8d42a7f6911401a940f8b43872cde0cbed
Timestamp: 1741031587 Timestamp [UCT]: 2025-03-03 19:53:07 Age [y:d:h:m:s]: 00:173:23:55:07
Block: 1231456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122177 RingCT/type: yes/0
Extra: 01cb9a7675acb49ebc2251dcc267303e8d42a7f6911401a940f8b43872cde0cbed0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6dd6f140bbea78e4898e2cb49a405cbe948671fe4de206c52659b83d3e21292 0.600000000000 1718363 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": 1231466, "vin": [ { "gen": { "height": 1231456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6dd6f140bbea78e4898e2cb49a405cbe948671fe4de206c52659b83d3e21292" } } ], "extra": [ 1, 203, 154, 118, 117, 172, 180, 158, 188, 34, 81, 220, 194, 103, 48, 62, 141, 66, 167, 246, 145, 20, 1, 169, 64, 248, 180, 56, 114, 205, 224, 203, 237, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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