Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c1e7dfaec953de93e4d4fb3f052029cf06ada5d4f269ca4edb435ac838ac81f

Tx prefix hash: e85bfc7931cdda4fdf8288b700cb7cd9fc60cc3765d808e2d4b279d4ec6ce847
Tx public key: 14c02a8d18b3641f3fcdc89ad0aa6a8885ede598d030e509cb8a426997ee71da
Timestamp: 1707603265 Timestamp [UCT]: 2024-02-10 22:14:25 Age [y:d:h:m:s]: 01:277:10:38:01
Block: 954772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457068 RingCT/type: yes/0
Extra: 0114c02a8d18b3641f3fcdc89ad0aa6a8885ede598d030e509cb8a426997ee71da02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a2a8283b9060655b9d8776d5d1944b62fa522e50f5b3a025ba63dd410b9dede 0.600000000000 1414054 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": 954782, "vin": [ { "gen": { "height": 954772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a2a8283b9060655b9d8776d5d1944b62fa522e50f5b3a025ba63dd410b9dede" } } ], "extra": [ 1, 20, 192, 42, 141, 24, 179, 100, 31, 63, 205, 200, 154, 208, 170, 106, 136, 133, 237, 229, 152, 208, 48, 229, 9, 203, 138, 66, 105, 151, 238, 113, 218, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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