Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7d1e54adfeaca427665230c7a607685fd8e7eef9b8caf21bff4461502662b6b

Tx prefix hash: 9f449eb2efb91bbb2403f94825de27eecd3006d19e2c5c5c53173b266bc5ab47
Tx public key: 751a3067c63eb437d2438cc16de6322b72a3c0a668e541fd6a841e45c29a7faa
Timestamp: 1736028237 Timestamp [UCT]: 2025-01-04 22:03:57 Age [y:d:h:m:s]: 00:164:02:58:39
Block: 1190308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116996 RingCT/type: yes/0
Extra: 01751a3067c63eb437d2438cc16de6322b72a3c0a668e541fd6a841e45c29a7faa021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fa10173f0acb865cfa86c3f98bee38af4e98fdf8290f9a8b03f92b8910cac9f 0.600000000000 1676823 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": 1190318, "vin": [ { "gen": { "height": 1190308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fa10173f0acb865cfa86c3f98bee38af4e98fdf8290f9a8b03f92b8910cac9f" } } ], "extra": [ 1, 117, 26, 48, 103, 198, 62, 180, 55, 210, 67, 140, 193, 109, 230, 50, 43, 114, 163, 192, 166, 104, 229, 65, 253, 106, 132, 30, 69, 194, 154, 127, 170, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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