Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 564dfda865165fa14af6dce9729f4a9ad0c85462f79026c1f20ae3e85d9f7b8b

Tx prefix hash: a707adad75386f93d40f63d5ff8c0352df83f4a5755953fbdc77c4949c3f5f87
Tx public key: a338e1e49a33ae2db7c2586a5ba804f46be0dff890cafc17f7a3eeb45c383fa2
Timestamp: 1733399520 Timestamp [UCT]: 2024-12-05 11:52:00 Age [y:d:h:m:s]: 01:056:16:51:29
Block: 1168538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298838 RingCT/type: yes/0
Extra: 01a338e1e49a33ae2db7c2586a5ba804f46be0dff890cafc17f7a3eeb45c383fa20211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42f100a2431db24cbe0746cddbe62e6f8c1fa83ef13a592c601ec2f55febb178 0.600000000000 1654247 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": 1168548, "vin": [ { "gen": { "height": 1168538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42f100a2431db24cbe0746cddbe62e6f8c1fa83ef13a592c601ec2f55febb178" } } ], "extra": [ 1, 163, 56, 225, 228, 154, 51, 174, 45, 183, 194, 88, 106, 91, 168, 4, 244, 107, 224, 223, 248, 144, 202, 252, 23, 247, 163, 238, 180, 92, 56, 63, 162, 2, 17, 0, 0, 0, 6, 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