Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32b286117e9569fd80e1c672b121b1eae5662caa774c9ef3d328d6de7e8584ab

Tx prefix hash: 134c558c40cfc0b0ad7b2dfca581fedebba011da6ffafaf7c257bf3249a831a0
Tx public key: 6cb15a3f655bcc46242f6f13363ac1988b4fb7727367be52cfd4fdf70bc1b14b
Timestamp: 1736604283 Timestamp [UCT]: 2025-01-11 14:04:43 Age [y:d:h:m:s]: 00:076:23:19:30
Block: 1195066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54788 RingCT/type: yes/0
Extra: 016cb15a3f655bcc46242f6f13363ac1988b4fb7727367be52cfd4fdf70bc1b14b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22c8daa4eb8dbdeba4fef229b8274bf4a2371e44c62a4a41b1bea93ba7a287cf 0.600000000000 1681651 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": 1195076, "vin": [ { "gen": { "height": 1195066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22c8daa4eb8dbdeba4fef229b8274bf4a2371e44c62a4a41b1bea93ba7a287cf" } } ], "extra": [ 1, 108, 177, 90, 63, 101, 91, 204, 70, 36, 47, 111, 19, 54, 58, 193, 152, 139, 79, 183, 114, 115, 103, 190, 82, 207, 212, 253, 247, 11, 193, 177, 75, 2, 17, 0, 0, 0, 3, 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