Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 890f1944ea867e595b5ae87a87b34f3605ec84ead68e6fb0c52afd7e19032164

Tx prefix hash: d0546f7555434c396a8d6dde3dc9584b95823884a23bc7b55d99c6d981c7ab21
Tx public key: ac550ca4fc945b514c436b02e7f80e2be3c696ddc7f3d83c281ef944a9f5fc28
Timestamp: 1720724420 Timestamp [UCT]: 2024-07-11 19:00:20 Age [y:d:h:m:s]: 00:252:22:25:17
Block: 1063568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180694 RingCT/type: yes/0
Extra: 01ac550ca4fc945b514c436b02e7f80e2be3c696ddc7f3d83c281ef944a9f5fc2802110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a4050a2eda87181ed2aaeaed04ce700d19d1783182aa564ffa5e266605000ae 0.600000000000 1534085 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": 1063578, "vin": [ { "gen": { "height": 1063568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a4050a2eda87181ed2aaeaed04ce700d19d1783182aa564ffa5e266605000ae" } } ], "extra": [ 1, 172, 85, 12, 164, 252, 148, 91, 81, 76, 67, 107, 2, 231, 248, 14, 43, 227, 198, 150, 221, 199, 243, 216, 60, 40, 30, 249, 68, 169, 245, 252, 40, 2, 17, 0, 0, 0, 15, 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