Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8269d64ba6df8c1f5c4eed7f9f1cc607287d6ee70446a38fff1d6f856638e164

Tx prefix hash: 48388ffb268a3ae285914b4165207da10660b2effafae0a6450c600350efcfe8
Tx public key: 1baa0f19f189e1c2297a087e8290b6f910755c418ef8b3c8d0a7134ca41fb14a
Timestamp: 1729611503 Timestamp [UCT]: 2024-10-22 15:38:23 Age [y:d:h:m:s]: 00:032:15:39:38
Block: 1137208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23323 RingCT/type: yes/0
Extra: 011baa0f19f189e1c2297a087e8290b6f910755c418ef8b3c8d0a7134ca41fb14a021100000001991650d1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f27f54b2a8c883ecc4998a643e363c271174437144df0ba8100540e47ef96064 0.600000000000 1620655 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": 1137218, "vin": [ { "gen": { "height": 1137208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f27f54b2a8c883ecc4998a643e363c271174437144df0ba8100540e47ef96064" } } ], "extra": [ 1, 27, 170, 15, 25, 241, 137, 225, 194, 41, 122, 8, 126, 130, 144, 182, 249, 16, 117, 92, 65, 142, 248, 179, 200, 208, 167, 19, 76, 164, 31, 177, 74, 2, 17, 0, 0, 0, 1, 153, 22, 80, 209, 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