Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91f00b932b593863e1b3abe96e35777171712f90b2c91d431ed6ee95e81f8b14

Tx prefix hash: 364cb8f50f08a78309c8cc5c61ceea7f8e497bd758e72898b9a71ada65f7e069
Tx public key: 31279b3d1457bdac175754cb6ba15e0971a23eff7f88aafc3c5b17ab2d6badca
Timestamp: 1735202285 Timestamp [UCT]: 2024-12-26 08:38:05 Age [y:d:h:m:s]: 00:095:19:58:27
Block: 1183471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68268 RingCT/type: yes/0
Extra: 0131279b3d1457bdac175754cb6ba15e0971a23eff7f88aafc3c5b17ab2d6badca021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 552deadcdfb34372e1c2d816c4dd48d5647dd43e4645b2a0aa01bb3c3d170f12 0.600000000000 1669916 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": 1183481, "vin": [ { "gen": { "height": 1183471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "552deadcdfb34372e1c2d816c4dd48d5647dd43e4645b2a0aa01bb3c3d170f12" } } ], "extra": [ 1, 49, 39, 155, 61, 20, 87, 189, 172, 23, 87, 84, 203, 107, 161, 94, 9, 113, 162, 62, 255, 127, 136, 170, 252, 60, 91, 23, 171, 45, 107, 173, 202, 2, 17, 0, 0, 0, 2, 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