Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e30f01fb1dccff79d60d2c66cddc03d419c60f9a3e03898c1a0b23e0d5450e9

Tx prefix hash: 5cf6f9e358c98787f073d1a2016adfc01c9652d7c9ab5605c1a1e42b1dd376b6
Tx public key: c9400e1486cc68daa373be2a1699ef06da36f8bd7b604dd33bec5bb45ea0502a
Timestamp: 1740306401 Timestamp [UCT]: 2025-02-23 10:26:41 Age [y:d:h:m:s]: 00:226:18:30:36
Block: 1225440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159775 RingCT/type: yes/0
Extra: 01c9400e1486cc68daa373be2a1699ef06da36f8bd7b604dd33bec5bb45ea0502a021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7c877e37122174749aec5c9a4e9abb39417d15763b9cabbcb3984f063d489f3 0.600000000000 1712305 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": 1225450, "vin": [ { "gen": { "height": 1225440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7c877e37122174749aec5c9a4e9abb39417d15763b9cabbcb3984f063d489f3" } } ], "extra": [ 1, 201, 64, 14, 20, 134, 204, 104, 218, 163, 115, 190, 42, 22, 153, 239, 6, 218, 54, 248, 189, 123, 96, 77, 211, 59, 236, 91, 180, 94, 160, 80, 42, 2, 17, 0, 0, 0, 6, 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