Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b493adce201be2a0aa52ade6bdc7dc78ae7d4cfba93a050506bcb79efe69e636

Tx prefix hash: 864e54409d4d4da8a35a098d65008b2ec11e0fce6209d27fe6412b39fccee28c
Tx public key: cca5a5cdfd2da1565e041f0e4e07bb8f3481c1565ad3274b8d0fc91ad355acb8
Timestamp: 1727526263 Timestamp [UCT]: 2024-09-28 12:24:23 Age [y:d:h:m:s]: 00:259:23:19:25
Block: 1119954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185555 RingCT/type: yes/0
Extra: 01cca5a5cdfd2da1565e041f0e4e07bb8f3481c1565ad3274b8d0fc91ad355acb802110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04a601570307a319249042817359603fea369ec34a5aa08f4f48c9278e1c8d03 0.600000000000 1601697 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": 1119964, "vin": [ { "gen": { "height": 1119954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04a601570307a319249042817359603fea369ec34a5aa08f4f48c9278e1c8d03" } } ], "extra": [ 1, 204, 165, 165, 205, 253, 45, 161, 86, 94, 4, 31, 14, 78, 7, 187, 143, 52, 129, 193, 86, 90, 211, 39, 75, 141, 15, 201, 26, 211, 85, 172, 184, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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