Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d276a7e5fb184eff7c983b68acf524b27d1c3b7751b6f3d0e44d5ea22ab51e6

Tx prefix hash: fc8fcef4a84df71eed8d9cc1222ce320910a2fc57323b64521040dcff375d4f7
Tx public key: 4b5f98d7b4818cd4e52f49ba1b046d387a0622c5a543eb784e8c93e4ba640782
Timestamp: 1722151594 Timestamp [UCT]: 2024-07-28 07:26:34 Age [y:d:h:m:s]: 00:252:08:43:06
Block: 1075391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180268 RingCT/type: yes/0
Extra: 014b5f98d7b4818cd4e52f49ba1b046d387a0622c5a543eb784e8c93e4ba64078202110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc7f4e9e70b144c3f6910c47cd46addd60dfb82b0db3f757bd5e0e7ead6924ea 0.600000000000 1547916 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": 1075401, "vin": [ { "gen": { "height": 1075391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc7f4e9e70b144c3f6910c47cd46addd60dfb82b0db3f757bd5e0e7ead6924ea" } } ], "extra": [ 1, 75, 95, 152, 215, 180, 129, 140, 212, 229, 47, 73, 186, 27, 4, 109, 56, 122, 6, 34, 197, 165, 67, 235, 120, 78, 140, 147, 228, 186, 100, 7, 130, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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