Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6356b1d2ef0060b7aabc80824515684bfa11f5dc8f4ff12b494299d203e028d1

Tx prefix hash: d00318549c7e5e00513881a8d4fd4d9b4dd0b30b19f580fe96c28ddfb74f3242
Tx public key: 55229fab1e739a5befb34ae3f2ec72fab1f5d55b123600d24d1f3ab694adced1
Timestamp: 1763200122 Timestamp [UCT]: 2025-11-15 09:48:42 Age [y:d:h:m:s]: 00:054:09:06:00
Block: 1412578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38941 RingCT/type: yes/0
Extra: 0155229fab1e739a5befb34ae3f2ec72fab1f5d55b123600d24d1f3ab694adced10211000000054e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02bed14bf268970fe791ba81273ed3e2e4e352212654ea1edf25a92dc1bf6846 0.600000000000 1901049 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": 1412588, "vin": [ { "gen": { "height": 1412578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02bed14bf268970fe791ba81273ed3e2e4e352212654ea1edf25a92dc1bf6846" } } ], "extra": [ 1, 85, 34, 159, 171, 30, 115, 154, 91, 239, 179, 74, 227, 242, 236, 114, 250, 177, 245, 213, 91, 18, 54, 0, 210, 77, 31, 58, 182, 148, 173, 206, 209, 2, 17, 0, 0, 0, 5, 78, 123, 252, 9, 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