Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 484aa3f863bf4baba2d37feea90bb1747a1da74af233413c60fd9583a1a4d6bb

Tx prefix hash: 2b9d1fb27fc346b49c173348bf9ddcee67446965d7a29f01d76db59eff16c73e
Tx public key: d5052a2464a4c4f6c8787abff4e6f33c1ecae381e628ec6356e1477a89f32699
Timestamp: 1729337738 Timestamp [UCT]: 2024-10-19 11:35:38 Age [y:d:h:m:s]: 00:200:03:46:11
Block: 1134964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142858 RingCT/type: yes/0
Extra: 01d5052a2464a4c4f6c8787abff4e6f33c1ecae381e628ec6356e1477a89f32699021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43136b3f8c22f2440f00c32f22339747043e9b224e635f9226c4bcbdc93dc283 0.600000000000 1618291 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": 1134974, "vin": [ { "gen": { "height": 1134964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43136b3f8c22f2440f00c32f22339747043e9b224e635f9226c4bcbdc93dc283" } } ], "extra": [ 1, 213, 5, 42, 36, 100, 164, 196, 246, 200, 120, 122, 191, 244, 230, 243, 60, 30, 202, 227, 129, 230, 40, 236, 99, 86, 225, 71, 122, 137, 243, 38, 153, 2, 17, 0, 0, 0, 7, 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