Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05f769a6b6d976d935aef37a0aec1eb6dfe0046600170a56b2cf18ff5a2507e5

Tx prefix hash: 659f2267eadc954271ab563e379f7cc1264e1d34041202ab04bdcdda7e0e5356
Tx public key: e2fc287dddac2ba5906bbfcf3b2d193c054508d7f51022a7f911124d1459a3c7
Timestamp: 1736686934 Timestamp [UCT]: 2025-01-12 13:02:14 Age [y:d:h:m:s]: 00:290:07:42:08
Block: 1195753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204995 RingCT/type: yes/0
Extra: 01e2fc287dddac2ba5906bbfcf3b2d193c054508d7f51022a7f911124d1459a3c70211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db8628f7117cd3014454c68069844b816ef21acbb3ce325f46a69c0151b1021b 0.600000000000 1682346 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": 1195763, "vin": [ { "gen": { "height": 1195753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db8628f7117cd3014454c68069844b816ef21acbb3ce325f46a69c0151b1021b" } } ], "extra": [ 1, 226, 252, 40, 125, 221, 172, 43, 165, 144, 107, 191, 207, 59, 45, 25, 60, 5, 69, 8, 215, 245, 16, 34, 167, 249, 17, 18, 77, 20, 89, 163, 199, 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