Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76860a5febf43e13b6d6850493213332e320149a6ec4da8eb0238e3fcacbb98c

Tx prefix hash: 7cc401a1cc058dc546c15da18e3e05dfb1aa28e68a9fce2f580c1b6f390c5562
Tx public key: 814c1c45092383c2ec55df2c153f7be720af675f6347e6dae38f64108e4d635f
Timestamp: 1738156330 Timestamp [UCT]: 2025-01-29 13:12:10 Age [y:d:h:m:s]: 00:138:15:23:54
Block: 1207657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99051 RingCT/type: yes/0
Extra: 01814c1c45092383c2ec55df2c153f7be720af675f6347e6dae38f64108e4d635f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f173e2ed05bbcf581e5e89b7ac2a488ad74f96f8e2d33b2445088d081bcb4540 0.600000000000 1694382 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": 1207667, "vin": [ { "gen": { "height": 1207657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f173e2ed05bbcf581e5e89b7ac2a488ad74f96f8e2d33b2445088d081bcb4540" } } ], "extra": [ 1, 129, 76, 28, 69, 9, 35, 131, 194, 236, 85, 223, 44, 21, 63, 123, 231, 32, 175, 103, 95, 99, 71, 230, 218, 227, 143, 100, 16, 142, 77, 99, 95, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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