Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b59c9ace9bead025080f5b5dbc20d7cdc3f65e8b6471bd544f05e6161772e5e6

Tx prefix hash: 65964b1bace0091f59c31622337398da407a45f62d234020e5e78e859657048b
Tx public key: 8f5956aa5330df0bbc9a5af590430d5265e7c4adaebfd08a1f135a5c00939287
Timestamp: 1720933031 Timestamp [UCT]: 2024-07-14 04:57:11 Age [y:d:h:m:s]: 00:274:16:21:15
Block: 1065297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196248 RingCT/type: yes/0
Extra: 018f5956aa5330df0bbc9a5af590430d5265e7c4adaebfd08a1f135a5c0093928702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a3f080590ddf4f215cb83386e04eafc0178a936706e2c29a55190512f19a253 0.600000000000 1535842 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": 1065307, "vin": [ { "gen": { "height": 1065297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a3f080590ddf4f215cb83386e04eafc0178a936706e2c29a55190512f19a253" } } ], "extra": [ 1, 143, 89, 86, 170, 83, 48, 223, 11, 188, 154, 90, 245, 144, 67, 13, 82, 101, 231, 196, 173, 174, 191, 208, 138, 31, 19, 90, 92, 0, 147, 146, 135, 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