Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 724a251937fc0e94310bd0fa1690525b90a7fc6d4a35f99fd7cfd8c0a943ad63

Tx prefix hash: d62a92b71ebc9779f1f0d049de1097ea08b1db2a1906db8bcf6e9c58c1685164
Tx public key: abfb769b773e0a0c5f68d7a3c8e8c2ac71544fc57b255684984f691f03749ec6
Timestamp: 1704552923 Timestamp [UCT]: 2024-01-06 14:55:23 Age [y:d:h:m:s]: 01:074:13:48:02
Block: 929475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314423 RingCT/type: yes/0
Extra: 01abfb769b773e0a0c5f68d7a3c8e8c2ac71544fc57b255684984f691f03749ec60211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf4f10bfb9142798ae5b83a216daf39db9eadc8ef8b2c65739ff74b1373da882 0.600000000000 1387351 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": 929485, "vin": [ { "gen": { "height": 929475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf4f10bfb9142798ae5b83a216daf39db9eadc8ef8b2c65739ff74b1373da882" } } ], "extra": [ 1, 171, 251, 118, 155, 119, 62, 10, 12, 95, 104, 215, 163, 200, 232, 194, 172, 113, 84, 79, 197, 123, 37, 86, 132, 152, 79, 105, 31, 3, 116, 158, 198, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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