Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac65f225a03ce47b572f759e7e85e9ce2637f9b4748d92888fd75c8877717b89

Tx prefix hash: 1b80c01190627d9ee07214b0929ee56a653eb6d450bd2b745ef67fd0b5a72e18
Tx public key: f6cec37fc952f86e08f41ad1fef8d3c9bf9594420fa0e88f4922134c789d1b3b
Timestamp: 1697679674 Timestamp [UCT]: 2023-10-19 01:41:14 Age [y:d:h:m:s]: 01:179:17:56:56
Block: 872710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389497 RingCT/type: yes/0
Extra: 01f6cec37fc952f86e08f41ad1fef8d3c9bf9594420fa0e88f4922134c789d1b3b021100000002faf35c9c000000000000000000

1 output(s) for total of 0.787679448000 dcy

stealth address amount amount idx
00: 5d729ff59b97ec0edfc0fec26c948f248ee4cbc845efc8616599cbac3919be96 0.787679448000 1327808 of 0

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": 872720, "vin": [ { "gen": { "height": 872710 } } ], "vout": [ { "amount": 787679448, "target": { "key": "5d729ff59b97ec0edfc0fec26c948f248ee4cbc845efc8616599cbac3919be96" } } ], "extra": [ 1, 246, 206, 195, 127, 201, 82, 248, 110, 8, 244, 26, 209, 254, 248, 211, 201, 191, 149, 148, 66, 15, 160, 232, 143, 73, 34, 19, 76, 120, 157, 27, 59, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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