Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f5b28d099f105123741ea70a1a290a2e7b21ee14c19543d34f95224440c4618

Tx prefix hash: 88e420abe8b35ce201ed42a0cb6f5fbff0d54af0af68b75daa200f5f7cbe9fe5
Tx public key: 41b431392d2ae5b66ffce00500523974b8cd08b3f24f904bf24293ff4b34b513
Timestamp: 1734801322 Timestamp [UCT]: 2024-12-21 17:15:22 Age [y:d:h:m:s]: 00:110:14:19:37
Block: 1180175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78814 RingCT/type: yes/0
Extra: 0141b431392d2ae5b66ffce00500523974b8cd08b3f24f904bf24293ff4b34b5130211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 129ce390b35698534f0df860a728ba42391e0ba5824393de6722f1a75b1f0f8f 0.600000000000 1666580 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": 1180185, "vin": [ { "gen": { "height": 1180175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "129ce390b35698534f0df860a728ba42391e0ba5824393de6722f1a75b1f0f8f" } } ], "extra": [ 1, 65, 180, 49, 57, 45, 42, 229, 182, 111, 252, 224, 5, 0, 82, 57, 116, 184, 205, 8, 179, 242, 79, 144, 75, 242, 66, 147, 255, 75, 52, 181, 19, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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