Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99a1136841c0c832292399c08fb1792c484246b51041dba0d3c3ea60762b071b

Tx prefix hash: a1b406d901adb0099b297c8955e88b3b6a2f5b89e1cbd38ce2ce7b5126afef68
Tx public key: 48a9e1dfaa7a6e0124a923527a695cf435258cdc8dcc03a7ad9c7327814c2acb
Timestamp: 1728475667 Timestamp [UCT]: 2024-10-09 12:07:47 Age [y:d:h:m:s]: 00:164:17:53:20
Block: 1127824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117532 RingCT/type: yes/0
Extra: 0148a9e1dfaa7a6e0124a923527a695cf435258cdc8dcc03a7ad9c7327814c2acb02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 219e3fd65755a478c031ce9023b46f3e38ddd69b4cafd926f29942269537e509 0.600000000000 1610637 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": 1127834, "vin": [ { "gen": { "height": 1127824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "219e3fd65755a478c031ce9023b46f3e38ddd69b4cafd926f29942269537e509" } } ], "extra": [ 1, 72, 169, 225, 223, 170, 122, 110, 1, 36, 169, 35, 82, 122, 105, 92, 244, 53, 37, 140, 220, 141, 204, 3, 167, 173, 156, 115, 39, 129, 76, 42, 203, 2, 17, 0, 0, 0, 1, 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