Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3a51b615440b1770394091ec57fbd355538f67f4901633ea339cb2cfa1d79d9

Tx prefix hash: 1321abe6f829c8343c67e91a516f39c741425f0aa80be4cc6de0940cbcb1ee25
Tx public key: ccec08108e6cd2c577859b5fce90675e66801a45895d8ce49dc1ea2d8e9ff0a9
Timestamp: 1720300625 Timestamp [UCT]: 2024-07-06 21:17:05 Age [y:d:h:m:s]: 01:134:01:05:43
Block: 1060041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354343 RingCT/type: yes/0
Extra: 01ccec08108e6cd2c577859b5fce90675e66801a45895d8ce49dc1ea2d8e9ff0a902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df73798f3d31c04f67afe65aa8cc182ee6715245ba3e7e8162c77d2f14e42245 0.600000000000 1530512 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": 1060051, "vin": [ { "gen": { "height": 1060041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df73798f3d31c04f67afe65aa8cc182ee6715245ba3e7e8162c77d2f14e42245" } } ], "extra": [ 1, 204, 236, 8, 16, 142, 108, 210, 197, 119, 133, 155, 95, 206, 144, 103, 94, 102, 128, 26, 69, 137, 93, 140, 228, 157, 193, 234, 45, 142, 159, 240, 169, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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