Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 958ea65df109527479f4a6cdad7f2d6f09154112e0048f7a34cc00ccfbba75d5

Tx prefix hash: 229562a7625c4d8263f3caaf79aa020af3619ba15a79f0d40e3a25c2abbba1d8
Tx public key: 2d5200d29f1a22d9cbb0f422c622bb73f69fe1bc1d41879508e3b8313e536d63
Timestamp: 1709072795 Timestamp [UCT]: 2024-02-27 22:26:35 Age [y:d:h:m:s]: 01:039:05:58:54
Block: 966976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289043 RingCT/type: yes/0
Extra: 012d5200d29f1a22d9cbb0f422c622bb73f69fe1bc1d41879508e3b8313e536d630211000000010546d7d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce2860ab5807878dd05ca23ca54808e0fafe4f0fa9fa01a8853078c9df50afc2 0.600000000000 1426747 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": 966986, "vin": [ { "gen": { "height": 966976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce2860ab5807878dd05ca23ca54808e0fafe4f0fa9fa01a8853078c9df50afc2" } } ], "extra": [ 1, 45, 82, 0, 210, 159, 26, 34, 217, 203, 176, 244, 34, 198, 34, 187, 115, 246, 159, 225, 188, 29, 65, 135, 149, 8, 227, 184, 49, 62, 83, 109, 99, 2, 17, 0, 0, 0, 1, 5, 70, 215, 208, 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