Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74052d28b6ed0c22c0a7303066d658312056be9b6679b9296983ecf95a1b7183

Tx prefix hash: 7d90b9f520cb2cf7e0b99ccedd9a3c04b396a41fce45a3dc741099d2cb8c3b7e
Tx public key: 4a758b40b6a427034104fd61bbb45ec8b39ffc69af0040a834f439b1f762e0db
Timestamp: 1737807390 Timestamp [UCT]: 2025-01-25 12:16:30 Age [y:d:h:m:s]: 00:148:07:44:46
Block: 1204992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105655 RingCT/type: yes/0
Extra: 014a758b40b6a427034104fd61bbb45ec8b39ffc69af0040a834f439b1f762e0db021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b5513dcfb560bb9238ba6e51a7b98e7961be93c117a75753bb7b1b794247f16 0.600000000000 1691687 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": 1205002, "vin": [ { "gen": { "height": 1204992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b5513dcfb560bb9238ba6e51a7b98e7961be93c117a75753bb7b1b794247f16" } } ], "extra": [ 1, 74, 117, 139, 64, 182, 164, 39, 3, 65, 4, 253, 97, 187, 180, 94, 200, 179, 159, 252, 105, 175, 0, 64, 168, 52, 244, 57, 177, 247, 98, 224, 219, 2, 17, 0, 0, 0, 7, 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